You can also save per-car FFB strength e.g. /ffb 10 into the car script file in data/script. For vanilla cars it’s e.g. XFG.lfs, for mods you have to use the 6-character Skin ID, e.g. 172CB8.lfs.

I like your suggestion - it would be more convenient if there was just one mapping name for each light type and we could have multiple colours of the same name.

The Terms & Conditions say this:

Quote :

2.4 Payment remainders can not be refunded.
2.5 Credit card and PayPal payments can only be refunded whole, within 30 days after purchase and as long as no copy of S1, S2 or S3 has been unlocked with the purchased license. Payments other than credit card or PayPal cannot be refunded.

This means that if you've bought an S1 license, your purchase can't be refunded.

Quote from Scawen :

And for anyone else reading, if you didn't notice, you can call these different mappings a different name, if there is a space after the special name.

E.g.
l_head standard
l_head retro
l_fog race
l_fog road

These will work as expected, as long as (e.g.) only one l_head xxx is used in one configuration.

This will be super useful I'm mapping a blue light beacon on one of my mods and I use the l_extra light mapping for it. Now I can only map the sides but there is no second mapping available to map the top part properly.

Quote from Scawen :

So I think the simple fix at that very complicated point of development, when the rim system was changed totally, was to make the tyre code draw what it does know about, that is the tyre cross section.

I think this is a good enough explanation It is not a real problem for me personally, I was just curious about the reason. It will just take some getting used to the tyre being visually shifted up (even though it is not).

Quote from Gutholz :

Maybe the thought is like this:
The caption on the button should be what happens if you click the button.
With this button you can "Unlock Live for Speed."

With it says "Demo racer" then it looks more like a status/information field. It does not look like something that you can click to perform an action.

Then it should say "Unlock Live for Speed" for S1 and S2 licensed users too, because they can still unlock additional content (I don't know if it does, I can't test that).

But it seems a bit strange seeing the same "unlock" button before and after logging in with a demo account.

The F9 tyre diagrams don't stretch all the way down in test patch:

0.7D


0.7D51


It looks like it's intentional but I didn't find it in the patch notes. Is it to have a clear separation between the dirt bar and the tyre?

I was just told that it is a feature introduced in 0.6T4:

Quote from Scawen :

Now "Unlock Live for Speed" instead of "Demo racer" on entry screen

I'm not sure what the reason behind it was.

When I unlock LFS as a demo racer, it still says "Unlock Live for Speed" on the entry screen, which can be confusing for people. I think it used to say "Demo racer: xxx" before, not sure when it changed to this. Maybe it is intentional but it looks like a bug to me.

When the connection list is open and you have "show pedals" enabled, the connection list moves left, which can obstruct the view, especially if the list is long.

I suggest to always keep the list on the right side and show the pedals on the left of it.

Current state:


Suggestion:

Quote :

New +/- buttons to adjust number of connections shown in N-list

If the scrollbar isn't visible, pressing these buttons seems to do the opposite of what I'd expect. Pressing "plus" makes the buttons smaller and I'd expect them to make the buttons bigger. Maybe the function of them should be "resize buttons" rather than "adjust number of connections"?

LOD2 and LOD3 don't have the correct mappings, can you please fix it?

With help from stuchlo, we have updated the Slovak translations.

Last edited by Flame CZE, Wed, 29 Nov 2023 19:52.

Quote from Androphp :

What you say is true, but Turkish players are playing the demo version not to test the game, but because they cannot get an S3 license and their computers are bad, and due to the low demo player limit, there are still at least 70-80 Turkish players playing in the 0.6R version, which I think is only in the 0.6R version right now. Turks play there are about 6-7 active servers. So, since the issue here is a budget issue, maybe bringing some innovation to the demo may encourage those players to switch to new versions.

If their computers are bad, playing with more players as you suggest would most likely make their experience worse. Enouraging them to switch to new demo versions doesn't bring any direct income to LFS.

If the car you're driving has all dashboard lights supported, you won't need to see the info message, a long as you can see the dashboard or have virtual gauges on.

If you use Shift+3, you might not know what states are in the cycle yet, so the message is helpful. But once you get to use the command, you've most likely already learnt all the possible states so the message would be more distracting in my opinion.

Since the test patch D50 introduced a few InSim updates, I've prepared a pull request to implement them in Node InSim.

Main additions:

License property added to IS_NCI packet
IS_PLH packet which sets handicaps for individual players
TINY_PLH subtype of IS_TINY to request IS_PLH listing player handicaps
SMALL_LCL subtype of IS_SMALL - full control of lights including fog and extra lights
Example app using OutGauge with InSim buttons
New dashboard lights in DashLights enum of OutGaugePack

Full list of changes in the PR: https://github.com/simbroadcasts/node-insim/pull/28

Ah sorry, I should've checked that before I posted

It still says "dipped" in the enum, that still needs updating

The DashLights and ShowLights properties of OutGaugePack will need to be updated at some point to include all the new light features.

But the packet doesn't seem to have much spare bytes to use

Quote from kristofferandersen :

Changing the strings was a good idea, i had not heard of dipped either. I refer to them as low/high beam.

I wanted to mention that it wouldn't remember the last light mode i had.
Reproduce: Shift+3 and set light mode to side. Press 3 twice and it will be set to dipped.

I believe i used the side lights. I just figured it was worth a mention.

That is intentional. Shift+3 cycles through side/low/high beam. Pressing 3 toggles low beam on/off only.

Quote from bayanofmansorofisky :

Yes indeed, there's also some key which i accidentally sometimes hit and it switches me to that tris subobject, i still don't know what are the keys on the keyboard to fast switch from tris tab

It is possible to do that in "sub" mode by pressing Ctrl + left mouse button (I think), but not in "tri" mode.

Quote from Günni92 :

Agreed. Though I am unable to find the option to change it - could you point it out to me?

Only reviewers can do that. If you send me links to the mods which you need to change to tweak mods, I can do it for you.

In fact I've added a "police" config on my local version of EMKO, which has an extra light that can be toggled using the new D50 command /light extra on/off/toggle

Quote from Gutholz :

Maybe have some scribbled red marker or tape on the RPM gauge.
(As if someone had marked the best upshift point)

Good idea

Quote from Gutholz :

]Also maybe have the trailer hitch only in the config with roof gear rack?
If I was to race this car, those two things would be my first changes.
(some applies for EMKO)

Sounds good, I will try to make use of all 8 possible configurations with the next update

In tri mode, when I try to select a triangle that is in a different subobject, it would be more helpful to show the custom name of the subobject instead of its type. For instance here it could say "triangle belongs to a subobject (dashboard)" because that's how I named it.

When all possible lights are enabled in dashboard editor, the list gets too long so the sliders for "neutral" are hidden.